We say the following

**Note:** Using a conda environment is the easiest way to satisfy the library's dependencies.

- Create the conda development environment:
Please install conda if you don't have it already. You can install it from [https://docs.conda.io/en/latest/miniconda.html](https://docs.conda.io/en/latest/miniconda.html)

I think it might be good to

1. Make a bit stronger statement that "is the easiest way to satisfy the library's dependencies". It sound like conda is really the only way to satisfy these dependencies. So maybe we should say

Building from source without conda is very difficult. We highly recommend that users build cuOpt inside a conda environment

2. Include instructions for installing miniconda. I worry a bit about pointing users to miniconda installation instructions. Maybe we could add one or two lines that show how to install miniconda?

We say the following

**Note:** Using a conda environment is the easiest way to satisfy the library's dependencies.

- Create the conda development environment:
Please install conda if you don't have it already. You can install it from [https://docs.conda.io/en/latest/miniconda.html](https://docs.conda.io/en/latest/miniconda.html)

I think it might be good to

1. Make a bit stronger statement that "is the easiest way to satisfy the library's dependencies". It sound like conda is really the only way to satisfy these dependencies. So maybe we should say

Building from source without conda is very difficult. We highly recommend that users build cuOpt inside a conda environment

2. Include instructions for installing miniconda. I worry a bit about pointing users to miniconda installation instructions. Maybe we could add one or two lines that show how to install miniconda?

Providing instruction on miniconda would add additional burden on us to make sure it is in working condition, it would be better if they can just go through miniconda website to install. And they might also have many options. and we might not want to limit them to number of options.

We say the following

**Note:** Using a conda environment is the easiest way to satisfy the library's dependencies.

- Create the conda development environment:
Please install conda if you don't have it already. You can install it from [https://docs.conda.io/en/latest/miniconda.html](https://docs.conda.io/en/latest/miniconda.html)

I think it might be good to

1. Make a bit stronger statement that "is the easiest way to satisfy the library's dependencies". It sound like conda is really the only way to satisfy these dependencies. So maybe we should say

Building from source without conda is very difficult. We highly recommend that users build cuOpt inside a conda environment

2. Include instructions for installing miniconda. I worry a bit about pointing users to miniconda installation instructions. Maybe we could add one or two lines that show how to install miniconda?

Providing instruction on miniconda would add additional burden on us to make sure it is in working condition, it would be better if they can just go through miniconda website to install. And they might also have many options. and we might not want to limit them to number of options.

But let me update the link that will take them directly to linux installation page

@chris-maes @rg20 May I get your review ?